While working on this, I noticed that calunga-push-to-pulp also calls create-advisory but doesn't have an embargo-check task. Should we add it there too? Maybe somewhere else?

Thanks for submitting a fix for this!
The embargo check task needs to read data generated by populate-release-notes task:

What populate-release-notes actually does for disk-images:

It runs the populate-release-notes-artifacts step, which:

Takes .releaseNotes.cves from the Release object + snapshot component structure
Populates .releaseNotes.content.artifacts[] with per-component entries that include linked CVEs
What embargo-check actually does without that populated data:

check-issues step — reads .releaseNotes.issues.fixed directly. This data comes from the Release object itself (via collect-data), not from populate-release-notes. So Jira issue visibility/embargo checking still works fine.
check-cves step — reads CVEs from .releaseNotes.content.artifacts. Without populate-release-notes, that field doesn't exist, so CVES="" → it logs "No CVEs found to check" and exits 0 silently. The InternalRequest to check-embargoed-cves is never made.
Cross-reference check (inside check-issues) — verifies a Jira Vulnerability's CVE ID appears in content.artifacts Without the populated artifacts, it hits line 239 ("No content found...") and continues rather than failing.

While working on this, I noticed that calunga-push-to-pulp also calls create-advisory but doesn't have an embargo-check task. Should we add it there too? Maybe somewhere else?

I don't think it's a bad idea to have for all pipelines unless I'm overlooking something. @johnbieren wdyt?

@jangel97 I wouldn't expect you to do it everywhere unless you just want to. We certainly appreciate the contribution!

While working on this, I noticed that calunga-push-to-pulp also calls create-advisory but doesn't have an embargo-check task. Should we add it there too? Maybe somewhere else?

I don't think it's a bad idea to have for all pipelines unless I'm overlooking something. @johnbieren wdyt?

@jangel97 I wouldn't expect you to do it everywhere unless you just want to. We certainly appreciate the contribution!

Any pipeline that creates an advisory should likely have the embargo-check task. I am not sure if it hurts to have embargo-check in all pipelines, but we'd have to look into it

@swickersh
I added populate-release-notes before embargo-check so that .releaseNotes.content.artifacts is
populated before the CVE embargo check runs.

The chain is now check-data-keys → populate-release-notes → embargo-check → push-disk-images. Matching how rh-advisories does it.

Please, let me know if anything else would be needed and thank you for the review!